3. Summary

Once again, this was a good event. We tried a new approach for testing — instead of trying to work through any bugs, we decided to continue testing all items that we could and only go back to fix bugs if they were holding up continuing with testing. This turned out to be a good approach and we were able to get the majority of vendor products tested.

Location turned out to be an important issue during the interop. Location appears to be useless in iCalendar. Some clients use locations, some do not. There needs to be a definition of properties that are absolutely required. Mozilla commented that they drop the location details on their recurrence items. Everyone wanted to be able to ingest location items and then know what to do with them. There may need to be extensions put in place within the specifications or via the Calsify efforts to handle them. Xprops are what need to be enhanced/fixed/resolved.

For the next interop, items to add to interop testing include:

• how many people use the language property on iCalendar objects

• how many can support daily savings time changes that will happen in 2007

• Free busy testing within CALDAV

• Tasks testing

• More testing of RFC2446 and RFC2447 scheduling events

• and the next phase of the CALDAV specification.

Following this report are the test results for the scenario testing for both CALDAV and the iCalendar specifications.

My thanks to everyone who furnished their notes and results.

Respectfully submitted,

Pat Egen
Interoperability Event Manager